Adjusting rate limits for transmission rates of data flows having a certain priority in a transmitter

ABSTRACT

A method for adjusting a set of primary rate limits for transmission rates of data flows having a certain priority in a transmitter is provided. A mean value is determined of a duty cycle of the certain priority at the port as obtainable from the transmission or flow control, wherein the data flows having different priorities including said certain priority are transmitted by a port of the transmitter, transmissions for rate-limited data flows having the certain priority are limited by secondary rate limits (r 1 ′, r 2 ′, . . . r n ′) per data flow, and transmissions for all data flows having the certain priority are controlled by a transmission or flow control per priority. The secondary rate limits (r 1 ′, r 2 ′, . . . r n ′) are obtained by adjusting the primary rate limits for the transmission rates of the data flows having the certain priority based on the determined mean value of the duty cycle.

The present application is a CONTINUATION of copending patentapplication Ser. No. 13/414,221.

FIELD OF THE INVENTION

The invention relates to a method for adjusting a set of primary ratelimits for transmission rates of data flows having a certain priority ina transmitter. Further, the invention relates to transmitting data flowshaving different priorities over one port.

BACKGROUND

In order to reduce congestion at bottlenecks in a network, transmissionsfor rate-limited data flows of a certain priority are limited by ratelimits per data flow that are established based upon feedback from thenetwork. Further, the transmissions for all data flows having thecertain priority are controlled or governed by a transmission or flowcontrol per priority.

High link speeds and short delays of data flows are provided byConverged Enhanced Ethernet (CEE) datacenters. CEE datacenters mayprovide lossless operation and lossless traffic classes beyond thetraditional lossy operation, in particular lossy traffic classes.

To avoid network congestion with effects such as head-of-line blockingand saturation trees, lossless CEE operation may require a distributedcongestion management (CM) according to IEEE 802.1Qau (QCN) withcongestion detection at so-called Congestion Points (CPs), the formationof Congestion Notification Messages (CNMs) sent to traffic sources, andrate limitation at the traffic sources in so-called Reaction Points(RPs).

Congestion Point (CP) is a VLAN-aware bridge or end station portfunction that monitors a single queue serving one or more priorityvalues. This queue, which may be referred to as CP buffer, can be placedat the output or input of a CEE switch or bridge, or at the input of anend station port function, and may be traversed by traffic from multiplesources and to multiple destinations.

The occupancy of the CP buffer can change due to temporary differencesbetween the overall arrival rate and the overall departure rate inbytes/second. When multiple priority values are supported, a separate CPbuffer is typically provided for each priority value. A QCN CP maydetermine the strength of congestion by taking into account the CPbuffer occupancy as well as its rate of change. A CP buffer can be asimple FIFO queue or, more generally, a portion of a Random AccessMemory (RAM).

For limiting the transmission rate of frames for one or morecongestion-controlled flows in response to receiving CNMs, a ReactionPoint (RP) may be used as an end-station port function. RPs may beprovided by a CEE-compliant Network Interface Card (NIC) or a ConvergedNetwork Adapter (CNA), which is a CEE-compliant NIC that providesadditional higher-layer functionality. An RP controls the transmissionrate of frames for one or more congestion-controlled flows by applying arate limit that may be updated dynamically. The rate limit is reducedmultiplicatively in response to receiving CNMs from congestion pointsand increased additively when a number of frames have been transmittedwithout receiving further CNMs, or when a self-increase timer haselapsed.

CEE switches and end-stations may employ priority-based flow control attheir receive queues for lossless operation. Priority-based Flow Control(PFC) may provide an independent flow control for the priority valuesand their associated receive queues. It prevents frame loss in receivequeues due to lack of space by sending PFC pause frames to the upstreamsender when one priority queue or multiple priority queues reach ahigh-water threshold, and by sending PFC unpause frames when the queuesare sufficiently drained to reach a low-water threshold. The receivequeues may be protected by both PFC and QCN. In such a case, the receivequeues are also QCN congestion points as described above. When a PFCpause frame, i.e., a PFC message with a positive pause duration, reachesa CEE-compliant NIC (also referred to as “NIC” in the following), theNIC pauses transmission for priorities that are selected by the PFCpause frame and for a duration specified in the PFC pause frame.

In accordance with QCN, PFC and Enhanced Transmission Selection ETS, aNIC transmitter typically uses a hierarchical scheduler. Thehierarchical scheduler may be comprised of a QCN scheduler stage forscheduling flows according to QCN rate limits, and of a PFC/ETSscheduler stage for scheduling priorities.

The QCN scheduler stage may have a flow scheduler for each priority andfor each port. The respective flow scheduler may select frames fortransmission from rate-limited flow queues by taking into account theearliest next departure time of each rate-limited flow according to itscurrent rate limit. Then, a transmission selection function may selectframes for transmission from different priorities or traffic classes,taking into account the pause state of each priority as provided, forexample, by PFC. Moreover, the transmission selection function may takeinto account any scheduling constraints, such as strict priorityscheduling or bandwidth allocation imposed on priorities or trafficclasses.

An interoperability problem between QCN and PFC may arise, because therate limits provided for the congestion-controlled flows of a priorityare further reduced by inserting transmission pauses for that priority.If QCN establishes the rate limits in a phase with considerable pauseactivity, then the effective rate limits are actually lower due to theinsertion of transmission pauses. For example, if a transmission linkpriority is used by multiple sources with an oversubscription ratio Ngreater than 1, then transmission pauses have to be inserted for thepriority with a pause on/off pattern, which effectively activates thepriority during a fraction 1/N of time.

When QCN has throttled the multiple sources sufficiently, the prioritytransitions from a PFC-dominated regime to a PFC-free regime. In case ofmany synchronized sources with a high oversubscription ratio N, thePFC-dominated regime has a correspondingly longer duration. One problemmay be that the transition of a priority to the PFC-free regime canoccur within a short amount of time, rapidly increasing the effectiverate limits for all rate-limited as well as for all non-rate-limitedflows of the priority. This may result in further PFC pauses on theadjacent link, aggravates congestion at downstream congestion points,and forces the downstream congestion points to send yet more CNMs. In asystem with many congestion points, this interaction between PFC and QCNmay reduce system stability and may lengthen the duration ofPFC-dominated regimes.

A flow control scheme such as PFC pause is necessary for losslessoperation, but is known to introduce side effects such as head-of-line(HOL) blocking and delay jitter. Therefore, in a system providing bothQCN and PFC, it may be important to control congestion as much aspossible using QCN rate limiting, and to apply PFC pause only as a lastresort to avoid frame loss.

The hierarchical scheduling that is necessary for a CEE-compliant NICtransmitter supporting QCN reaction points as well as PFC and ETS mayintroduce an undesirable coupling between the effective fine-grainedper-flow QCN rate limits and the coarse-grained per-priority pause andinter-priority scheduling activities as introduced, for example, by PFCand ETS, respectively. As a result, QCN rate limits of rate-limitedflows may become incorrect or inaccurate when pause activity starts orstops gating transmission of an entire priority, or when inter-priorityscheduling changes the bandwidth available to a priority.

Accordingly, it is an aspect of the present invention to provide asolution for reducing the undesirable coupling between the effectivefine-grained per-flow rate limits and the coarse-grained per-prioritypause and inter-priority scheduling activities.

SUMMARY

According to a first aspect, a device for adjusting a set of primaryrate limits for transmission rates of data flows having a certainpriority in a transmitter is suggested, wherein data flows havingdifferent priorities including said certain priority are transmitted bya port of the transmitter. Transmissions for rate-limited data flowshaving the certain priority are limited by secondary rate limits perdata flow and transmissions for all data flows having the certainpriority are controlled or governed by a transmission or flow controlper priority. The device comprises a determiner and a number ofadjusters. The determiner is configured to determine a mean value of aduty cycle of the certain priority at the port as obtainable from thetransmission or flow control. The adjusters are configured to obtain thesecondary rate limits by adjusting the primary rate limits for thetransmission rates of the data flows having the certain priority basedon the determined mean value of the duty cycle.

In particular, the respective primary rate limit is multiplied with areciprocal value of the determined mean value of the duty cycle value toobtain the respective secondary rate limit. The data flows of saiddifferent priorities are transmitted by the port of the transmitteracross a data link. The mean value of the duty cycle corresponds to thefraction of time during which transmission at the certain priority isnot suspended as a result of priority pause or flow control indicationsfrom a downstream receiver coupled to the data link, or as a result ofinter-priority scheduling activity.

Further, the device may have a flow scheduler for scheduling thetransmission of the data flows having the certain priority subject tothe secondary rate limits for the data flows and to the transmission orflow control for the entire priority.

According to some implementations, the secondary rate limit for therate-limited data flows is obtained such that the primary rate limit aswell as the effective rate limit approaches a value that is suitable foran ideal priority duty cycle of 1 and is, in particular, at least in afirst-order approximation, independent of the actual duty cycle of thecertain priority at the port. Thus, the undesirable coupling between theeffective fine-grained per-flow rate limits and the coarse-grainedper-priority pause and inter-priority scheduling activities affectingthe duty cycle of the certain priority at the port may be prevented.

In an embodiment, the device comprises a rate limiter and an adjusterfor each rate-limited data flow having the certain priority. The ratelimiter is configured to provide a primary rate limit for thetransmission rate. The adjuster is configured to obtain a secondary ratelimit by adjusting the provided primary rate limit based on thedetermined mean value of the duty cycle.

Further, the adjuster may be configured to multiply the primary ratelimit with a reciprocal value of the determined mean value of the dutycycle value to obtain the secondary rate limit.

In particular, the adjuster may be configured to calculate acompensation factor as a reciprocal value of the determined mean dutycycle value and to multiply the primary rate limit by the calculatedcompensation factor.

In a further embodiment, the device may include the functionality of oneor more reaction points. Specifically, each included reaction point mayprovide a receiver that is configured to receive messages identifyingthe corresponding rate-limited data flow as a source of congestion andto control the primary rate limit of the rate limiter. In particular,the receiver of each reaction point is configured to receive CongestionNotification Messages (CNMs) for computing the primary rate limit.

In a further embodiment, the device may include a flow scheduler for thecertain priority, in particular for each priority of the differentpriorities. The flow scheduler is configured to schedule thetransmission of data frames across the rate-limited as well asnon-rate-limited data flows having the certain priority on the basis ofthe secondary rate limit of each rate-limited data flow and may takeinto account a corresponding earliest next departure time.

In a further embodiment, the device comprises a selector for eachrate-limited data flow of the certain priority. The selector isconfigured to select a minimum of the secondary rate limit and of amaximum rate that is configured for the certain priority.

In a further embodiment, the device comprises a flow scheduler for thecertain priority, in particular for each priority of the differentpriorities, where the flow scheduler of the certain priority isconfigured to schedule the transmission of data frames across therate-limited data flows on the basis of the selected minimum of thesecondary rate limit and of the maximum rate and may take into account acorresponding earliest next departure time for each rate-limited dataflow.

In a further embodiment, the device includes a rate-limited flow queuefor each data flow of the certain priority, a flow multiplexer for thecertain priority coupled to the rate-limited flow queues and the flowscheduler for the certain priority for controlling the flow multiplexer.The flow scheduler may perform its scheduling by using the earliest nextdeparture times computed by individual schedulers of the data flows.

The flow scheduler may additionally control the flow multiplexer using around-robin scheme to select a data flow for transmission from the dataflows that have frames on their flow queues and are eligible to sendbased on their secondary rate limits or the resulting earliest nextdeparture times.

In a further embodiment, the determiner has a low-pass filter forproviding the mean value of the duty cycle of the certain priority byfiltering a binary-valued signal indicating that the transmission at thecertain priority is currently active or suspended at the port due to theflow control for the certain priority. The mean value of the duty cycleof the certain priority may also be determined by averaging the dutycycle of the certain priority over any sliding window of time andthrough any other averaging method.

In a further embodiment, the certain priority is flow-controlled bymeans of per-priority pause and unpause signalling. The per-prioritypause and unpause signalling is also referred to as Priority-based FlowControl (PFC).

In a further embodiment, the certain priority is selected fortransmission based on per-priority pause and unpause signalling as wellas inter-priority scheduling constraints, such as strict priorityscheduling and bandwidth allocation to priorities.

In a further embodiment, transmission for the certain priority iscontrolled by means of per-priority pause and unpause signalling (PFC)or any other per-priority flow control scheme, and by inter-priorityscheduling constraints. The inter-priority scheduling constraints may beimposed by Enhanced Transmission Selection (ETS). Thus, the certainpriority is selected for transmission subject to inter-priorityscheduling constraints and per-priority flow control.

In a further embodiment, the device has a reaction point (RP) for eachrate-limited data flow having the certain priority p. In particular, theRPs may be configured to eliminate the need to adjust the rate limits ofall rate-limited flows of a priority p as a result of increased ordecreased PFC pause activity due to temporary overload and/or schedulingchanges resulting from ETS scheduling constraints. The RP has arate-limited flow queue for the rate-limited data flow having thecertain priority p, a rate limiter for providing the primary rate limitr_(n) for the transmission rate for the rate-limited data flow, amultiplier for multiplying the primary rate limit r_(n) with acompensation factor c_(p)(t) to obtain the secondary rate limit r_(n)′(r₁; =r_(n)·c_(p)(t)), a selector for selecting a minimum r_(n)″ of thesecondary rate limit r_(n)′ and of a maximum rate R_(p) that isconfigured for the certain priority p (r_(n)″=min(r_(n)t, R_(p)).

The following example may illustrate this: Suppose that a NIC transmitport is subject to T-periodic PFC pauses for priority p, with a priorityduty cycle d_(p)=τ/T, where 0<d_(p)≦1.

When PFC pause activity gates the QCN rate limiter with current rater_(n), an effective rate limit r_(eff,n)=d_(p)·r_(n) results.

First, an estimate d_(p)(t)≦1 of the priority duty cycle is determined.The estimate d_(p)(t) represents the fraction of time the priority p isactive. Second, a feedback is provided from the priority duty cycledeterminer or estimator to the RP, where the rate limit r_(n) of the QCNrate limiter is divided by the estimated duty cycle d_(p)(t) and cappedat a maximum rate R_(p) to obtain a modified rate limit r_(n)″.r _(n)″=min(r _(n) /d _(p)(t),R _(p))≧min(r _(n) ,R _(p))  (1)

Third, the modified rate limit r_(n)″ is used for scheduling in the QCNscheduler stage of the NIC hierarchical scheduler.

The flow-specific QCN control loop in combination with the priorityduty-cycle compensation may let the QCN rate limiter of the present RPconverge to a primary rate limit, which corresponds to an ideal priorityduty cycle of 1 and is, to a first-order approximation, independent ofthe actual priority duty cycle.

The priority duty cycle may depend on the collective behavior of allflows of the priority, including flows that are not yet or no longer QCNrate-limited. Moreover, the priority duty cycle may change rapidly as aresult of a change in total offered load, whereas a QCN rate limit maychange rarely in comparison, particularly if many flows aresimultaneously active.

As a result of the PFC/ETS scheduler stage of the NIC hierarchicalscheduler, the modified rate limit r_(n)″ is further modified to aneffective rate limitr _(eff,n) =d _(p)(t)·r _(n)″=min(r _(n) ,d _(p)(t)·R _(p)).  (2)

Equation (2) shows that the effective rate limit of a flow is given bythe QCN rate limit r_(n), unless r_(n) exceeds d_(p)(t)·R_(p), themaximum rate possible for a single flow. This means that, in a region oflinearity, the adaptation of the QCN rate limit r_(n) absorbs the ratereduction due to the insertion of priority pauses and inter-priorityscheduling, i.e., it absorbs the multiplicative rate reduction factord_(p)(t)<1. The transmission may be suspended for a priority andtherefore d_(p)(t)<1, due to PFC pauses or ETS scheduling constraints.In a region of linearity, priority duty-cycle compensation thus ensuresthat both PFC pause activity and ETS scheduling constraints acrosspriorities are taken into account and in fact absorbed by the stochasticadaptation of the QCN rate limiters, where the speed of adaptation tothe PFC and ETS constraints is given by the adaptation gains and timeconstants of the QCN feedback loops.

A rapid reduction of the priority duty cycle is needed for losslessnessin temporary overload scenarios with many sources, where QCN may havedifficulties to throttle the many sources quickly enough for avoidingPFC pauses. It may be noted that a PFC pause globally affects all flowsof a priority, even those which are not yet, or no longer, QCNrate-limited. An advantage of the present priority duty-cyclecompensation may be that a reduction of the priority duty-cycle forresolving temporary overload conditions first and foremost reduces thethroughput of flows that are not currently QCN rate-limited. At the sametime, priority duty-cycle compensation may reduce the need to furtheradjust the rate limits of flows that already are QCN rate-limited.

There are congestive scenarios with many synchronized sources, wheresynchronized PFC oscillations may occur on multiple links of a systemover considerable durations. It was found through simulations thatpriority duty-cycle compensation greatly speeds up the convergence ofQCN rate limiters in the presence of such PFC oscillations and therebyreduces the duration of undesirable phases of operation that aredominated by PFC pause activity and associated head-of-line (HOL)blocking.

Any embodiment of the first aspect may be combined with any embodimentof the first aspect to obtain another embodiment of the first aspect.

According to a second aspect, the invention relates to a transmitter fortransmitting data flows having different priorities over one port. Thetransmitter has a device for each certain priority of the differentpriorities according to the first aspect or according to any embodimentof the first aspect. The respective device has at least one determiner,one rate limiter for each rate-limited data flow having the certainpriority and one adjuster for each rate-limited data flow having thecertain priority. The respective rate limiter is configured to provide aprimary rate limit for the transmission rate of the respective dataflow. The determiner is configured to determine a mean value of a dutycycle of the certain priority at the port. The respective adjuster isconfigured to obtain a secondary rate limit by adjusting the respectiveprovided primary rate limit based on the determined mean value of theduty cycle.

In an embodiment, the transmitter is embodied by a Converged EnhancedEthernet (CEE) compliant Network Interface card (NIC). Moreover, thetransmitter may be embodied by a switch or gateway.

In a further embodiment, the transmitter comprises a hierarchicalscheduler. The hierarchical scheduler may have a QCN scheduler stage forscheduling flows according to QCN rate limits, and a PFC/ETS schedulerstage for scheduling priorities.

According to a third aspect, a method for adjusting a set of primaryrate limits for transmission rates of data flows having a certainpriority in a transmitter is suggested. Data flows having differentpriorities including said certain priority are transmitted by a port ofthe transmitter. Transmissions for rate-limited data flows having thecertain priority are limited by secondary rate limits per data flow andtransmissions for all data flows having the certain priority aregoverned by a transmission or flow control per priority. The method hasa step of determining a mean value of a duty cycle of the certainpriority at the port, where the duty cycle of the certain priority isprovided by the transmission or flow control. Furthermore, the methodhas a step of obtaining the secondary rate limits by adjusting theprimary rate limits for the transmission rates of the data flows havingthe certain priority based on the determined mean value of the dutycycle

According to a fourth aspect, the invention relates to a computerprogram comprising a program code for executing the method of the thirdaspect for adjusting a set of primary rate limits for transmission ratesof data flows having a certain priority in a transmitter when run on atleast one computer.

In the following disclosure, example embodiments of the presentinvention are described with reference to the enclosed figures.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a schematic block diagram of a first embodiment of a devicefor adjusting a set of primary rate limits for transmission rates ofdata flows having a certain priority in a transmitter,

FIG. 2 shows a schematic block diagram of a second embodiment of adevice for adjusting a set of primary rate limits for transmission ratesof data flows having a certain priority in a transmitter,

FIG. 3 shows a schematic block diagram of an embodiment of a low-passfilter for providing a compensation factor for duty-cycle correction,

FIG. 4 shows a schematic block diagram of a first embodiment of atransmitter for transmitting data flows having different priorities overone port,

FIG. 5 shows a schematic block diagram of a second embodiment of atransmitter for transmitting data flows having different priorities overone port,

FIG. 6 shows an embodiment of a sequence of method steps for adjusting aset of primary rate limits for transmission rates of data flows having acertain priority in a transmitter, and

FIG. 7 shows a schematic block diagram of an embodiment of a systemadapted for performing the method for adjusting a set of primary ratelimits for transmission rates of data flows having a certain priority ina transmitter

Similar or functionally similar elements in the figures have beenallocated the same reference signs if not otherwise indicated.

DETAILED DESCRIPTION

In FIG. 1, a schematic block diagram of a first embodiment of a device100 for adjusting a set of primary rate limits r₁, r₂ for transmissionrates of data flows having a certain priority in a transmitter isdepicted. The primary rate limits may be obtained based on congestionfeedback per data flow from the network.

Data flows of different priorities including said certain priority aretransmitted by a port of the transmitter. Transmissions of the dataflows having the certain priority are limited by secondary rate limitsr₁′, r₂′ per data flow and by a transmission of flow control perpriority. The device 100 has a determiner 101 and two adjusters 102,103.

Without loss of generality, FIG. 1 shows only two primary rate limitsr₁, r₂ for the transmission rates of two rate-limited data flows havingthe certain priority. Thus, the device 100 of FIG. 1 comprises twoadjusters, namely a first adjuster 102 for a primary rate limit r₁ and asecond adjuster 103 for a primary rate limit r₂.

Because the transmission of the data flow having the certain priority islimited at the port, there is a duty cycle of the certain priority atthe port effected by the transmission or flow control per priority.

The determiner 101 is configured to determine a mean value d_(p)(t) ofthe duty cycle of the certain priority at the port.

The first adjuster 102 is configured to adjust the primary rate limit r₁for the transmission rate of a first rate-limited data flow having thecertain priority based on the determined mean value d_(p)(t) of the dutycycle to obtain a secondary rate limit r₁′ for the first rate-limiteddata flow. In particular, the primary rate limit r₁ is multiplied with areciprocal value of the determined mean value d_(p)(t) of the duty cycleto output the secondary rate limit r₁′.

Further, the second adjuster 103 is configured to adjust a primary ratelimit r₂ for the transmission rate of a second rate-limited data flowhaving the certain priority based on the determined mean value d_(p)(t)of the duty cycle to obtain a secondary rate limit r₂′ for the secondrate-limited data flow.

Particularly, the primary rate limit r₂ is also multiplied with thereciprocal value of the determined mean value d_(p)(t) to output thesecondary rate limit r₂′.

The secondary rate limits r₁′, r₂′ for the two rate-limited data flowsare obtained such that each of the primary rate limits approaches avalue that is suitable for an ideal priority duty cycle of 1. Hence, theprimary rate limits become, in a first-order approximation, independentof the current duty cycle of the certain priority at the port.

FIG. 2 shows a schematic block diagram of a second embodiment of adevice 100 for adjusting a set of primary rate limits r₁, r₂ fortransmission rates of data flows having the certain priority in atransmitter.

The second embodiment of the device 100 of FIG. 2 is based on the firstembodiment of the device 100 of FIG. 1 and has all above-mentionedfeatures of the first embodiment.

Further, the device 100 of FIG. 2 has a first rate limiter 104 and asecond rate limiter 105.

The first rate limiter 104 is coupled to the first adjuster 102. Thefirst rate limiter 104 is configured to provide the first primary ratelimit r₁ for the transmission rate of the first rate-limited data flow.

In an analogous way, the second rate limiter 105 is coupled to thesecond adjuster 103 and provides the second primary limit r₂.

The respective rate limiter 104, 105 has a receiver (not shown as adistinct unit) that is configured to receive messages m₁, m₂ identifyingthe respective rate-limited data flow as a source of congestion forcontrolling the primary rate limit r₁, r₂ of the rate limiter 104, 105.

For example, the first rate limiter 104 receives messages m₁ identifyingthe first rate-limited data flow as a source of congestion and controlsthe primary rate limit r₁ in dependence on the received messages m₁.Further, the second rate limiter 105 receives messages m₂ identifyingthe second rate-limited data flow as a source of congestion and controlsthe primary rate limit r₂ in dependence on the received messages m₂.

In FIG. 3, a schematic block diagram of an embodiment of a low-passfilter 300 for providing a compensation factor c_(p)(t) for duty cyclecorrection is depicted. The low-pass filter 300 may be part of thedeterminer 101 of FIG. 1 or FIG. 2.

The compensation factor c_(p)(t) may correspond to the reciprocal valueof the determined mean value d_(p)(t) of the duty cycle value of thecertain priority (see FIGS. 1 and 2).

The low-pass filter 300 has a first multiplier 301, an adder 302, a timedelay element 303, a second multiplier 304 and a reciprocal element 305outputting a reciprocal value of a received input. The time delayelement 305 has a time constant of 100 μs, for example.

The low-pass filter 300 is configured to provide the mean value d_(p)(t)of the duty cycle of the certain priority by filtering a binary signala_(p)(t). The binary signal a_(p)(t) indicates that a transmission atthe certain priority is currently active or suspended at the port due tothe flow control for the certain priority. For example, a “1” of thebinary signal a_(p)(t) may indicate that the certain priority iscurrently active. Further, a “0” of the binary signal a_(p)(t) mayindicate that the certain priority is currently suspended, in particularpaused.

The low-pass filter 300 may be a first-order low-pass filter, with aweighting factor w such that 0<w<1. For example, w=0.99.

In FIG. 4, a schematic block diagram of a first embodiment of atransmitter 400 for transmitting data flows having different prioritiesover one port is illustrated. Of course, the transmitter 400 may have aplurality of ports.

Without loss of generality, FIG. 4 shows only one device for schedulingdata flows having one certain priority p of said different priorities.If the transmitter 400 is configured to transmit data flows of Pdifferent priorities, the transmitter is comprised with P devices asshown in FIG. 4 and explained in the following.

The device for scheduling the certain priority p of the transmitter 400of FIG. 4 has a flow segregator 401 for the certain priority p, onereaction point (RP) 402, 403 for each rate-limited data flow f₁-f_(n)having the certain priority p, a queue 404 for non-rate-limited dataflows f_(n+1), a flow scheduler 405 and a flow multiplexer 406.

For illustration reasons, FIG. 4 shows only two reaction points 402,403, namely the reaction point 402 for a first rate-limited data flow f₁having the certain priority p and the reaction point 403 for a n-thrate-limited data flow f_(n) having the certain priority p. Between thereaction point 402 and the reaction point 403, there are (n−2) furtherreaction points for (n−2) further rate-limited data flows having thecertain priority p.

The reaction points 402, 403 and the further reaction points (not shown)may be constructed equally.

The reaction point 402 comprises a rate-limited flow queue 407 for thefirst rate-limited data flow f₁ having the certain priority p. Further,the reaction point 402 has a rate limiter 408 for providing a primaryrate limit r₁ for the transmission rate of the first rate-limited dataflow f₁. A multiplier 409 is coupled to the rate limiter 408. Themultiplier 409 is configured to multiply the primary rate limit r₁ witha compensation factor c_(p)(t) to obtain the secondary rate limit r₁′.The compensation factor c_(p)(t) corresponds to a reciprocal value ofthe determined mean value of the duty cycle value. The compensationfactor c_(p)(t) may be obtained as explained above, for example withreference to FIG. 3.

Further, the reaction point 402 has a selector 410. The selector 410receives the secondary rate limit r₁′ as well as a maximum rate R_(p)that is configured for the certain priority p. The selector 410 selectsthe minimum of the received signals and outputs the selected minimum r₁″to a scheduler 411 (r₁″=min(r₁′, R_(p)). The scheduler 411 outputs anearliest next departure time t_(ND,1) for the first data flow f₁ basedon the received minimum r₁″.

The reaction point 403 has a rate-limited flow queue 412 for the n-thrate-limited data flow f_(n) having the certain priority p. Further, thereaction point 403 has a rate limiter 413 for providing a primary ratelimit r_(n) for the transmission rate of the n-th rate-limited data flowf_(n). A multiplier 414 is coupled to the rate limiter 413. Themultiplier 414 is configured to multiply the primary rate limit r_(n)with the compensation factor c_(p)(t) to obtain the secondary rate limitr_(n)′. A selector 415 receives the secondary rate limit r_(n)′ as wellas the maximum rate R_(p) that is configured for the certain priority p.The selector 415 selects the minimum of the received signals and outputsthe selected minimum r_(n)″ to a scheduler 416 (r_(n)″=min(r_(n)′,R_(p)). A scheduler 416 outputs an earliest next departure time t_(ND,n)for the n-th data flow f_(n) based on the received minimum r_(n)″.

The flow scheduler 405 is configured to schedule the transmission ofdata frames across the rate-limited data flows f₁-f_(n) having thecertain priority p on the basis of the received earliest next departuretimes t_(ND,1)-t_(ND,n).

Based on the received earliest next departure times t_(ND,1)-t_(ND,n),the flow scheduler 405 controls the flow multiplexer 406 which iscoupled to the rate-limited flow queues 407 and 412 for the rate-limiteddata flows f₁ and f_(n), respectively, and to the queue 404 for thenon-rate-limited data flows f_(n+1). The flow multiplexer 406 outputs ascheduled data flow for the priority p.

In particular, the device of FIG. 4 may be embodied by a QCN schedulerstage for scheduling the data flows of a certain priority according toQCN rate limits.

In FIG. 5, a schematic block diagram of a second embodiment of atransmitter 400 for transmitting data flows having different prioritiesover one port is illustrated.

The second embodiment of the transmitter 400 of FIG. 5 is based on thefirst embodiment of the transmitter 400 of FIG. 4 and has allabove-mentioned features of the first embodiment.

The transmitter 400 further has a respective flow multiplexer 417 forthe respective further certain priority of the different priorities. Forillustration reasons, only one further flow multiplexer 417 is shown inFIG. 5.

In an analogous way, FIG. 5 shows only two transmission queues 418, 419coupled to the flow multiplexers 406, 407. In general, the number oftransmission queues equals the number of priorities or, equivalently,the number of flow multiplexers in the transmitter 400. In detail, theflow multiplexer 406 is coupled towards the transmission queue 418 forone certain priority of the different priorities, and the flowmultiplexer 417 is coupled towards a further transmission queue 419 fora further certain priority of the different priorities.

All transmission queues 418, 419 are coupled to a transmission selector420 for the coupled port 421. The transmission selector 411 isconfigured to select frames for transmission from the differenttransmission queues 418, 419 corresponding to the different priorities.The transmission selector 420 may take into account a pause state ofeach priority and any scheduling constraints, such as strict-priorityscheduling and bandwidth allocation, imposed on priorities or trafficclasses by IEEE 801.1Qaz Enhanced Transmission Selections (ETS).

In this regard, the transmission selector 420 is configured to receivemessages s₁ indicating or including transmitted PFC pauses and messagess₂ indicating or including received PFC pauses. The transmissionselector 420 outputs scheduled data flows over all different prioritiesto the coupled port 421 of the transmitter.

FIG. 6 shows an embodiment of a sequence of method steps for adjusting aset of primary rate limits for transmission rates of data flows having acertain priority in a transmitter.

It may be noted that by one port of the transmitter, data flows ofdifferent priorities including said certain priority are transmitted.The transmission of the data flows having the certain priority islimited by the secondary rate limits per data flow and by a transmissionor flow control per priority.

In step 601, a mean value of a duty cycle of the certain priority at theport is determined. The duty cycle of the certain priority at the portmay be provided by the transmission or flow control.

In step 602, the secondary rate limits are obtained by adjusting theprimary rate limits for the transmission rates of the data flows havingthe certain priority are adjusted based on the determined mean value ofthe duty cycle.

Computerized devices can be suitably designed for implementingembodiments of the present invention as described herein. In thatrespect, it can be appreciated that the methods described herein arelargely non-interactive and automated. In example embodiments, themethods described herein can be implemented either in an interactive,partly-interactive or non-interactive system. The methods describedherein can be implemented in software (e.g., firmware), hardware, or acombination thereof. In example embodiments, the methods describedherein are implemented in software, as an executable program, the latterexecuted by suitable digital processing devices. In further exampleembodiments, at least one step of above method of FIG. 6 is implementedin software, as an executable program, the latter executed by suitabledigital processing devices. In further example embodiments, thedetermining step and the obtaining step of above method of FIG. 6 areimplemented in software, in particular for the case that the duty cycleof the certain priority at the port is provided the that software. Moregenerally, embodiments of the present invention can be implementedwherein general-purpose digital computers, such as personal computers,workstations, etc., are used.

For instance, the system 700 depicted in FIG. 7 schematically representsa computerized unit 701, e.g., a general-purpose computer. In exampleembodiments, in terms of hardware architecture, as shown in FIG. 7, theunit 701 includes a processor 705, memory 710 coupled to a memorycontroller 715, and one or more input and/or output (I/O) devices 740,745, 750, 755 (or peripherals) that are communicatively coupled via alocal input/output controller 735. The input/output controller 735 canbe, but is not limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The input/output controller 735 mayhave additional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, toenable communications. Further, the local interface may include address,control, and/or data connections to enable appropriate communicationsamong the aforementioned components.

The processor 705 is a hardware device for executing software,particularly that stored in memory 710. The processor 705 can be anycustom made or commercially available processor, a central processingunit (CPU), an auxiliary processor among several processors associatedwith the computer 701, a semiconductor based microprocessor (in the formof a microchip or chip set), or generally any device for executingsoftware instructions.

The memory 710 can include any one or combination of volatile memoryelements (e.g., random access memory) and nonvolatile memory elements.Moreover, the memory 710 may incorporate electronic, magnetic, optical,and/or other types of storage media. Note that the memory 710 can have adistributed architecture, where various components are situated remotefrom one another, but can be accessed by the processor 705.

The software in memory 710 may include one or more separate programs,each of which comprises an ordered listing of executable instructionsfor implementing logical functions. In the example of FIG. 7, thesoftware in the memory 710 includes methods described herein inaccordance with example embodiments and a suitable operating system (OS)711. The OS 711 essentially controls the execution of other computerprograms, such as the methods as described herein (e.g., FIG. 6), andprovides scheduling, input-output control, file and data management,memory management, and communication control and related services.

The methods described herein may be in the form of a source program,executable program (object code), script, or any other entity comprisinga set of instructions to be performed. When in a source program form,then the program needs to be translated via a compiler, assembler,interpreter, or the like, as known per se, which may or may not beincluded within the memory 710, so as to operate properly in connectionwith the OS 711. Furthermore, the methods can be written as an objectoriented programming language, which has classes of data and methods, ora procedure programming language, which has routines, subroutines,and/or functions.

Possibly, a conventional keyboard 750 and mouse 755 can be coupled tothe input/output controller 735. Other I/O devices 740-755 may includesensors (especially in the case of network elements), i.e., hardwaredevices that produce a measurable response to a change in a physicalcondition like temperature or pressure (physical data to be monitored).Typically, the analog signal produced by the sensors is digitized by ananalog-to-digital converter and sent to controllers 735 for furtherprocessing. Sensor nodes are ideally small, consume low energy, areautonomous and operate unattended.

In addition, the I/O devices 740-755 may further include devices thatcommunicate both inputs and outputs. The system 700 can further includea display controller 725 coupled to a display 730. In exampleembodiments, the system 700 can further include a network interface ortransceiver 760 for coupling to a network 765.

The network 765 transmits and receives data between the unit 701 andexternal systems. The network 765 is possibly implemented in a wirelessfashion, e.g., using wireless protocols and technologies, such as WiFi,WiMax, etc. The network 765 may be a fixed wireless network, a wirelesslocal area network (LAN), a wireless wide area network (WAN) a personalarea network (PAN), a virtual private network (VPN), intranet or othersuitable network system and includes equipment for receiving andtransmitting signals.

The network 765 can also be an IP-based network for communicationbetween the unit 701 and any external server, client and the like via abroadband connection. In example embodiments, network 765 can be amanaged IP network administered by a service provider. Besides, thenetwork 765 can be a packet-switched network such as a LAN, WAN,Internet network, etc.

If the unit 701 is a PC, workstation, intelligent device or the like,the software in the memory 710 may further include a basic input outputsystem (BIOS). The BIOS is stored in ROM so that the BIOS can beexecuted when the computer 701 is activated.

When the unit 701 is in operation, the processor 705 is configured toexecute software stored within the memory 710, to communicate data toand from the memory 710, and to generally control operations of thecomputer 701 pursuant to the software. The methods described herein andthe OS 711, in whole or in part are read by the processor 705, typicallybuffered within the processor 705, and then executed. When the methodsdescribed herein (e.g. with reference to FIG. 6) are implemented insoftware, the methods can be stored on any computer readable medium,such as storage 720, for use by or in connection with any computerrelated system or method.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects. Furthermore, aspectsof the present invention may take the form of a computer program productembodied in one or more computer readable medium(s) having computerreadable program code embodied thereon. Any combination of one or morecomputer readable medium(s) may be utilized. The computer readablemedium may be a computer readable signal medium or a computer readablestorage medium. A computer readable storage medium may be, for example,but not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of the computer readable storage medium would include thefollowing: an electrical connection having one or more wires, a harddisk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a magnetic storage device, or any suitablecombination of the foregoing. In the context of this document, acomputer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device. Program codeembodied on a computer readable medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, etc., or any suitable combination of theforegoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on the unit701, partly thereon, partly on a unit 701 and another unit 701, similaror not.

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams can be implemented by one or morecomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblocks may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved and algorithmoptimization. It will also be noted that each block of the blockdiagrams and/or flowchart illustration, and combinations of blocks inthe block diagrams and/or flowchart illustration, can be implemented byspecial purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

More generally, while the present invention has been described withreference to certain embodiments, it will be understood by those skilledin the art that various changes may be made and equivalents may besubstituted without departing from the scope of the present invention.In addition, many modifications may be made to adapt a particularsituation to the teachings of the present invention without departingfrom its scope. Therefore, it is intended that the present invention notbe limited to the particular embodiments disclosed, but that the presentinvention will include all embodiments falling within the scope of theappended claims.

The invention claimed is:
 1. A method for adjusting a set of primaryrate limits for transmission rates of data flows in a transmitter,comprising: determining, for a certain priority and at a port in thetransmitter, a mean value of a duty cycle, wherein the mean value of theduty cycle is calculated using a fraction of time during whichtransmission at the certain priority is not suspended according to atransmission or flow control, wherein data flows having differentpriorities, including a data flow having the certain priority, aretransmitted by the port of the transmitter, transmissions forrate-limited data flows having the certain priority are limited by a setof secondary rate limits (r₁′, r₂′, . . . r_(n)′) per data flow, andtransmissions for all data flows having the certain priority arecontrolled by the transmission or flow control per priority; andcomputing the set of secondary rate limits (r₁′, r₂′, . . . r_(n)′) byadjusting a corresponding set of primary rate limits for thetransmission rates of the data flows having the certain priority basedon the determined mean value of the duty cycle.